Use VTScada

Use this section to learn how to create and use VTScada applications. Topics are organized more or less in the order you are likely to need the information as you progress from installation, through development, and then to managing a completed system.

Options During Installation:

  • Choose to download maps as required. Applies only to Open Street Map providers. Carto maps are enabled regardless, so long as the server has an Internet connection, but may be disabled through configuration later.
  • Registration: Installation key or use VTScadaLIGHT. See notes for Using VTScadaLIGHT.
  • Change the installation folder if required. Some system integrators choose to maintain multiple versions of VTScada by installing each in its own folder.
  • Exclude portions of the program including the documentation and the tools for testing and debugging. Choose this only to save space on servers where no development work will be done.
  • Select either 32-bit or 64-bit architecture. 64-bit is recommended in most cases unless you are installing on older hardware or operating system.
  • Allow reporting of limited usage statistics to Trihedral. Not optional for VTScadaLIGHT licenses. Customers who have purchased an installation key may choose whether to provide statistics to Trihedral.
  • Install VTScada as a Windows Service. Do not choose this option until you have created the application that will run on that server and configured it to run automatically. It is also recommended that you first configure the VTScada Thin Client Server so that you can create thin client connections to your application using the VTScada Internet Client, Mobile Client or Anywhere Client.

System administrators can do a silent install of VTScada. Contact Trihedral Technical Support for instructions that will be relevant to your situation.

Keep a tidy development environment. If you leave the Application Properties dialog open while you (or others) work on other tasks, you can expect to see warnings that settings may have changed, even though the change may have been to a file that doesn't affect configuration properties. Also, while a tag properties dialog is open, certain other development tools will not open.
When moving from one development tool to another, unless you plan to return to the first immediately, it is better practice to close the first window before opening the second.